Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat_: use content-topic override for all community filters #5993

Draft
wants to merge 3 commits into
base: feat/comm-content-topic-poc
Choose a base branch
from

Conversation

chaitanyaprem
Copy link
Contributor

@chaitanyaprem chaitanyaprem commented Oct 25, 2024

This is second phase of content-topic changes for communities where single content-topic is used for sending as well as receiving. This is follow-up change of #5864 and should be released only once all users have migrated to a version using #5864 as this change breaks compatibility for communities and users on any version before #5864.

Important changes:

  • Both send and receive in communities is done via single content-topic
  • Basic validation of community messaging with phase-1 changes
  • validation of non community messaging with 2.30 and phase-1 changes
  • Dogfooding by other team members
  • All community feature validation by QA
  • If possible , release phase-2 as well along with phase-1 changes for new communities that would be created . But rollout 2 phases separately for existing communities as being discussed here [Deliverable] Review usage of content topics in Status Communities protocol waku-org/pm#268 (comment). @osmaczko would it be as simple as adding a communityVersion field in communityDescription? Wondering if all existing communities can be labelled as version 1 and communities created after this change be version 2 and use the version to determine how content-topics shall be used.

@status-im-auto
Copy link
Member

status-im-auto commented Oct 25, 2024

Jenkins Builds

Click to see older builds (16)
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ f3352d2 #1 2024-10-25 10:07:21 ~4 min ios 📦zip
✔️ f3352d2 #1 2024-10-25 10:08:07 ~5 min linux 📦zip
✖️ f3352d2 #1 2024-10-25 10:08:59 ~6 min tests-rpc 📄log
✔️ f3352d2 #1 2024-10-25 10:09:04 ~6 min android 📦aar
✖️ f3352d2 #1 2024-10-25 10:36:11 ~33 min tests 📄log
✔️ f803523 #2 2024-10-29 11:08:30 ~2 min android 📦aar
✔️ f803523 #2 2024-10-29 11:08:46 ~2 min linux 📦zip
✔️ f803523 #2 2024-10-29 11:09:13 ~3 min ios 📦zip
✖️ f803523 #2 2024-10-29 11:12:17 ~6 min tests-rpc 📄log
✖️ f803523 #3 2024-10-29 11:37:24 ~2 min tests-rpc 📄log
✖️ f803523 #2 2024-10-29 11:40:03 ~34 min tests 📄log
✔️ f028f84 #3 2024-10-29 12:22:42 ~3 min ios 📦zip
✔️ f028f84 #3 2024-10-29 12:24:53 ~5 min linux 📦zip
✔️ f028f84 #3 2024-10-29 12:25:35 ~5 min android 📦aar
✖️ f028f84 #4 2024-10-29 12:27:01 ~7 min tests-rpc 📄log
✖️ f028f84 #3 2024-10-29 12:59:16 ~39 min tests 📄log
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ cb59e06 #4 2024-10-30 04:28:07 ~3 min android 📦aar
✔️ cb59e06 #4 2024-10-30 04:28:22 ~3 min linux 📦zip
✔️ cb59e06 #5 2024-10-30 04:29:23 ~4 min tests-rpc 📄log
✔️ cb59e06 #1 2024-10-30 04:29:31 ~4 min macos 📦zip
✔️ cb59e06 #4 2024-10-30 04:30:25 ~5 min ios 📦zip
✔️ cb59e06 #1 2024-10-30 04:32:45 ~8 min macos 📦zip
✖️ cb59e06 #1 2024-10-30 04:35:56 ~11 min windows 📦zip
✖️ cb59e06 #2 2024-10-30 04:53:15 ~10 min windows 📦zip
✔️ cb59e06 #4 2024-10-30 04:58:23 ~33 min tests 📄log
✔️ 54b1cd7 #6 2024-11-01 08:27:44 ~2 min tests-rpc 📄log
✔️ 54b1cd7 #2 2024-11-01 08:30:41 ~5 min macos 📦zip
✔️ 54b1cd7 #5 2024-11-01 08:30:54 ~5 min linux 📦zip
✔️ 54b1cd7 #5 2024-11-01 08:31:16 ~5 min android 📦aar
✔️ 54b1cd7 #5 2024-11-01 08:31:38 ~6 min ios 📦zip
✔️ 54b1cd7 #2 2024-11-01 08:35:29 ~10 min macos 📦zip
✖️ 54b1cd7 #3 2024-11-01 08:36:51 ~11 min windows 📦zip
✔️ 54b1cd7 #5 2024-11-01 08:59:53 ~34 min tests 📄log

Copy link

codecov bot commented Oct 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.58%. Comparing base (d61d200) to head (54b1cd7).

Additional details and impacted files
@@                       Coverage Diff                       @@
##           feat/comm-content-topic-poc    #5993      +/-   ##
===============================================================
- Coverage                        60.60%   60.58%   -0.03%     
===============================================================
  Files                              812      812              
  Lines                           109344   109346       +2     
===============================================================
- Hits                             66266    66245      -21     
- Misses                           35321    35328       +7     
- Partials                          7757     7773      +16     
Flag Coverage Δ
functional 13.02% <14.28%> (-0.07%) ⬇️
unit 59.94% <100.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
protocol/messenger_communities.go 53.33% <100.00%> (-0.06%) ⬇️
protocol/transport/filters_manager.go 75.70% <100.00%> (+0.06%) ⬆️

... and 30 files with indirect coverage changes

@chaitanyaprem chaitanyaprem marked this pull request as draft October 30, 2024 10:38
Copy link
Contributor

@osmaczko osmaczko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chaitanyaprem can you please rebase, the diff seems wrong, thanks 🙏

@chaitanyaprem chaitanyaprem force-pushed the feat/comm-content-topic-poc branch 2 times, most recently from b5315d5 to 103b415 Compare November 1, 2024 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants